Main controller for telematics integration functioning concurrently as a telematics client node and a telematics host node

ABSTRACT

A main controller may be used to provide integrated, centralized, and optimized handling of telematics data in welding arrangements. The main controller may receive from other components of a welding arrangement, telematics data, and may apply at least some processing to the telematics data, to enable use of the telematics data by a remote entity. The telematics data may comprises data relating to an engine used in driving one or more components of the welding arrangement, data relating to one or more components of the welding arrangement, and/or data relating to welding operations performed via the welding arrangement. The processing of telematics data may comprise formatting data in accordance with a single standard format, digitizing analog data, and/or processing data for communication to the remote entity. The main controller may provide telematics client and/or host node functions, such as based on the controller area network (CANBus) protocol.

CLAIM OF PRIORITY

This patent application is a continuation of U.S. Provisional patentapplication Ser. No. 15/070,888, filed on Mar. 15, 2016, which in turnmakes reference to, claims priority to and claims benefit from U.S.Provisional Patent Application Ser. No. 62/134,417, filed on Mar. 17,2015. Each of the above identified applications is hereby incorporatedherein by reference in its entirety.

BACKGROUND

Welding has increasingly become ubiquitous in all industries. Weldingcan be performed in automated manner or in manual manner (e.g., beingperformed by a human). However, while welding may be automated incertain contexts, a large number of applications continue to exist wheremanual welding operations are used (e.g., where a welding operator usesa welding gun or torch to perform the welding). In either mode(automated or manual), the success of welding operations relies heavilyon proper use of the welding equipment.

BRIEF SUMMARY

Various implementations of the present disclosure are directed to maincontroller for telematics integration, substantially as illustrated byor described in connection with at least one of the figures, as setforth more completely in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example system that may be used for welding-typeoperations, in accordance with aspects of the present disclosure.

FIG. 2 shows example welding equipment in accordance with aspects of thepresent disclosure.

FIG. 3 is a block diagram illustrating an example main controller systemfor telematics integration, in accordance with aspects of the presentdisclosure.

FIG. 4A is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party telematics, andwithout engine control unit (ECU).

FIG. 4B is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party telematics, andwith engine control unit (ECU).

FIG. 5A is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party telematics andtelematics modules, and without engine control unit (ECU).

FIG. 5B is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party telematics andtelematics modules, and with engine control unit (ECU).

FIG. 6A is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party wirelesscommunication components, and without engine control unit (ECU).

FIG. 6B is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party wirelesscommunication components and engine control unit (ECU).

FIG. 7A is a block diagram illustrating an example configuration forcontrolling telematics integration using internal wireless communicationcomponents, and without engine control unit (ECU).

FIG. 7B is a block diagram illustrating an example configuration forcontrolling telematics integration using internal wireless communicationcomponents, and with engine control unit (ECU).

DETAILED DESCRIPTION

FIG. 1 shows an example system that may be used for welding-typeoperations, in accordance with aspects of this disclosure. In thisregard, “welding-type” operations may comprise operations in accordancewith any known welding technique, including flame welding techniquessuch as oxy-fuel welding, electric welding techniques such as shieldedmetal arc welding (i.e., stick welding), metal inert gas welding (MIG),tungsten inert gas welding (TIG), resistance welding, as well as gouging(e.g., carbon arc gouging), cutting (e.g., plasma cutting), brazing,induction heating, soldering, and/or the like. Referring to FIG. 1,there is shown an example welding arrangement 10 in which an operator 18is wearing welding headwear 20 and welding a workpiece 24 using a torch30 to which power is delivered by equipment 12 via a conduit 14, withweld monitoring equipment 28, which may be available for use inmonitoring welding operations. The equipment 12 may comprise a powersource, optionally a source of an inert shield gas and, wherewire/filler material is to be provided automatically, a wire feeder.Further, in some instances an engine 32 may be used to drive equipmentor components used during welding operations. For example, the engine 32may drive generators, power sources, etc. used during weldingoperations.

The welding arrangement 10 of FIG. 1 may be configured to form a weldjoint by any known welding-type technique.

Optionally in any embodiment, the welding equipment 12 may be arcwelding equipment that provides a direct current (DC) or alternatingcurrent (AC) to a consumable or non-consumable electrode 16 of a torch30. The electrode 16 delivers the current to the point of welding on theworkpiece 24. In the welding arrangement 10, the operator 18 controlsthe location and operation of the electrode 16 by manipulating the torch30 and triggering the starting and stopping of the current flow. Whencurrent is flowing, an arc 26 is developed between the electrode and theworkpiece 24. The conduit 14 and the electrode 16 thus deliver currentand voltage sufficient to create the electric arc 26 between theelectrode 16 and the workpiece. The arc 26 locally melts the workpiece24 and welding wire or rod supplied to the weld joint (the electrode 16in the case of a consumable electrode or a separate wire or rod in thecase of a non-consumable electrode) at the point of welding betweenelectrode 16 and the workpiece 24, thereby forming a weld joint when themetal cools.

Optionally in any embodiment, the weld monitoring equipment 28 may beused to monitor welding operations. The weld monitoring equipment 28 maybe used to monitor various aspects of welding operations, particularlyin real-time (that is as welding is taking place). For example, the weldmonitoring equipment 28 may be operable to monitor arc characteristicssuch as length, current, voltage, frequency, variation, and instability.Data obtained from the weld monitoring may be used (e.g., by theoperator 18 and/or by an automated quality control system) to ensureproper welding.

As shown, the equipment 12 and headwear 20 may communicate via a link 25via which the headwear 20 may control settings of the equipment 12and/or the equipment 12 may provide information about its settings tothe headwear 20. Although a wireless link is shown, the link may bewireless, wired, or optical.

Optionally in any embodiment, equipment or components used duringwelding operations may be driven using engines. For example, the engine32 may drive generators, power sources, etc. used during weldingoperations. In some instances, it may be desired to obtain informationrelating to used engines. For example, data relating to engines (andoperations thereof) used during welding operations may be collected andused (e.g., based on analysis thereof) in monitoring and optimizingoperations of these engines. The collection and use of such data may beperformed telematically—that is, the data may be collected locally,subjected to at least some processing locally (e.g., formatting, etc.),and then may be communicated to remote management entities (e.g.,centralized management locations, engine providers, etc.), usingwireless technologies (e.g., cellular, satellite, etc.). In variousexample embodiments, a dedicated controller (e.g., shown as element 34in FIG. 1) may be used to control, centralize, and/or optimize datahandling operations. The controller 34 may comprise suitable circuitry,hardware, software, or any combination thereof for use in performingvarious aspects of the engine related data handling operations. Forexample, the controller 34 may be operable to interface with the engine32 to obtain data related thereto. The interfacing (or obtaining data)may be done via analog sensors and/or via electronic engine control unit(ECU) if one is present. Further, the controller 34 may be operable totrack or obtain welding related data (e.g., from weld monitoringequipment 28, from equipment 12, etc.). The controller 34 may thentransmit the data (e.g., both engine related and weld related data),such as to facilitate remote monitoring and/or management, by way ofwireless communications. In particular, this may be done by use ofcellular and or satellite telematics hardware, for example. An exampleimplementation is described in more detail with respect to FIG. 3.

FIG. 2 shows example welding equipment in accordance with aspects ofthis disclosure. The equipment 12 of FIG. 2 comprises an antenna 202, acommunication port 204, communication interface circuitry 206, userinterface module 208, control circuitry 210, power supply circuitry 212,wire feeder module 214, and gas supply module 216.

The antenna 202 may be any type of antenna suited for the frequencies,power levels, etc. used by the communication link 25.

The communication port 204 may comprise, for example, an Ethernet overtwisted pair port, a USB port, an HDMI port, a passive optical network(PON) port, and/or any other suitable port for interfacing with a wiredor optical cable.

The communication interface circuitry 206 is operable to interface thecontrol circuitry 210 to the antenna 202 and/or port 204 for transmitand receive operations. For transmit, the communication interface 206may receive data from the control circuitry 210 and packetize the dataand convert the data to physical layer signals in accordance withprotocols in use on the communication link 25. For receive, thecommunication interface may receive physical layer signals via theantenna 202 or port 204, recover data from the received physical layersignals (demodulate, decode, etc.), and provide the data to controlcircuitry 210.

The user interface module 208 may comprise electromechanical interfacecomponents (e.g., screen, speakers, microphone, buttons, touchscreen,etc.) and associated drive circuitry. The user interface 208 maygenerate electrical signals in response to user input (e.g., screentouches, button presses, voice commands, etc.). Driver circuitry of theuser interface module 208 may condition (e.g., amplify, digitize, etc.)the signals and them to the control circuitry 210. The user interface208 may generate audible, visual, and/or tactile output (e.g., viaspeakers, a display, and/or motors/actuators/servos/etc.) in response tosignals from the control circuitry 210.

The control circuitry 210 comprises circuitry (e.g., a microcontrollerand memory) operable to process data from the communication interface206, the user interface 208, the power supply 212, the wire feeder 214,and/or the gas supply 216; and to output data and/or control signals tothe communication interface 206, the user interface 208, the powersupply 212, the wire feeder 214, and/or the gas supply 216.

The power supply circuitry 212 comprises circuitry for generating powerto be delivered to a welding electrode via conduit 14. The power supplycircuitry 212 may comprise, for example, one or more voltage regulators,current regulators, inverters, and/or the like. The voltage and/orcurrent output by the power supply circuitry 212 may be controlled by acontrol signal from the control circuitry 210. The power supplycircuitry 212 may also comprise circuitry for reporting the presentcurrent and/or voltage to the control circuitry 210. In an exampleimplementation, the power supply circuitry 212 may comprise circuitryfor measuring the voltage and/or current on the conduit 14 (at either orboth ends of the conduit 14) such that reported voltage and/or currentis actual and not simply an expected value based on calibration.

The wire feeder module 214 is configured to deliver a consumable wireelectrode 16 to the weld joint. The wire feeder 214 may comprise, forexample, a spool for holding the wire, an actuator for pulling wire offthe spool to deliver to the weld joint, and circuitry for controllingthe rate at which the actuator delivers the wire. The actuator may becontrolled based on a control signal from the control circuitry 210. Thewire feeder module 214 may also comprise circuitry for reporting thepresent wire speed and/or amount of wire remaining to the controlcircuitry 210. In an example implementation, the wire feeder module 214may comprise circuitry and/or mechanical components for measuring thewire speed, such that reported speed is actual and not simply anexpected value based on calibration.

The gas supply module 216 is configured to provide shielding gas viaconduit 14 for use during the welding process. The gas supply module 216may comprise an electrically controlled valve for controlling the rateof gas flow. The valve may be controlled by a control signal fromcontrol circuitry 210 (which may be routed through the wire feeder 214or come directly from the control 210 as indicated by the dashed line).The gas supply module 216 may also comprise circuitry for reporting thepresent gas flow rate to the control circuitry 210. In an exampleimplementation, the gas supply module 216 may comprise circuitry and/ormechanical components for measuring the gas flow rate such that reportedflow rate is actual and not simply an expected value based oncalibration.

FIG. 3 is a block diagram illustrating an example main controller systemfor telematics integration, in accordance with aspects of the presentdisclosure. Shown in FIG. 3 is a main controller 300, one or more enginesensors 360, external 3rd party communication equipment 362, an enginecontrol unit (ECU) 364, legacy 3rd party telematics units 370 ₁ and 370₂, external telematics unit 380, and one or more additional pieces ofequipment which may use or be affected by telematics information(including, e.g., “next generation” equipment, such as next generationweld control communication (WCC) unit 392, next generation welding userinterface (UI) 394, next generation machine user interface (UI) 396,etc.).

Each of the one or more engine sensors 360 may comprise suitablehardware, software, or combination thereof for collecting and/oroutputting sensory data relating to engines, operations thereof,environmental or operational parameters affecting the engines, and/orcomponents used in conjunction with engines and/or affect the engines'operations. For example the sensors 360 may comprise an auxiliary powertransformer sensor 360 ₁, a battery voltage sensor 360 ₂, and one ormore engine sensors 360 ₃ (which may provide sensory readings relatingto such parameters or components as coolant temperature, level (low)coolant, oil pressure, oil sender, fuel sender, oil sender switch,etc.). The sensors 360 (and data generated thereby) may be analog.

The main controller 300 may comprise suitable hardware, software, orcombination thereof for providing main control functions for telematicsintegration. For example, the main controller 300 may comprise a mainprocessor 310, an internal communication subsystem 320, an externalcommunication interface component 330, a telematics client component340, and a telematics host component 350.

The main processor 310 is operable to process data, execute particulartasks or functions (e.g., relating to operations performed by the maincontroller 300), and/or control operations of other components in themain controller 300. The main processor 310 may be a general purposeprocessor (e.g., CPU), a special purpose processor (e.g., ASIC), etc.The disclosure is not limited to a particular type of processor,however.

For example, the main processor 310 may receive data associated withtelematics related functions or operations, and may process that data(e.g., including formatting the data based on an applicable formattingstandard), such as for wireless communication to remote telematicsmonitoring and/or management entities. In this regard, the maincontroller 300 may comprise suitable interface components (e.g.,circuitry, hardware, software, or any combination thereof) forfacilitating reception of the telematics related data and/or forenabling interactions with components or devices providing that data.The telematics related data may comprise digital and/or analog data, andmay comprise location, machine status, service info, engine sensor data,error codes, and other data available to the main controller 300. Thedata may include, for example, welding related data 301, sensory relateddata 303, and/or telematics data obtained from ECUs or 3rd partytelematics units. In this regard, the telematics client component 340may be configured to function as a telematics node, such as a controllerarea network (CANBus) node, to communicate with ECUs (e.g., theelectronic ECU 364). The communications may for example use a CANBusbased communication protocol to obtain engine data 341 provided by theelectronic ECU 364. The data may then be input (as input signal 305)into the main processor 310.

Once the telematics related data is collected and processed (includingformatting) for communication, the main processor 310 may communicate(e.g., wirelessly) the processed-for-communication telematics data usingavailable communication components. For example, where an internalcommunication component is present (e.g., internal communicationsubsystem 320), the processed-for-communication telematics data may beforwarded to that component, via corresponding control signals 311, fortransmission thereby. Alternatively, where external communicationcomponents are used (e.g., the external 3rd party communicationequipment 362), the processed-for-communication telematics data may besent to these components, such as via the external communicationinterface component 330. In this scenario, the external communicationcomponent 330 may receive the processed-for-communication telematicsdata as signal 315, and apply any necessary processing (e.g., TCP/IPprocessing) to facilitate communication to the external equipment 362.

The internal communication subsystem 320 may comprise suitable circuitryoperable to handle communications in the main controller 300. Theinternal communication subsystem 320 may comprise, for example, atransceiver configured to support various wired or wirelesstechnologies. For example, the internal communication subsystem 320 maybe operable to configure, setup, and/or use wired and/or wirelessconnections, such as over suitable wired/wireless interface(s) and inaccordance with wireless and/or wired protocols or standards supportedin the device, to facilitate transmission and/or reception of signals(e.g., carrying data). Further, the internal communication subsystem 320may be operable to process transmitted and/or received signals, inaccordance with applicable wired or wireless technologies. Examples ofwireless technologies that may be supported and/or used by the internalcommunication subsystem 320 may comprise wireless personal area network(WPAN), such as Bluetooth (IEEE 802.15); near field communication (NFC);wireless local area network (WLAN), such as WiFi (IEEE 802.11); cellulartechnologies, such as 2G/2G+(e.g., GSM/GPRS/EDGE, and IS-95 or cdmaOne)and/or 3G/3G+(e.g., CDMA2000, UMTS, and HSPA); 4G, such as WiMAX (IEEE802.16) and LTE; Ultra-Wideband (UWB); etc. Examples of wiredtechnologies that may be supported and/or used by the internalcommunication subsystem 320 comprise Ethernet (IEEE 802.3), UniversalSerial Bus (USB) based interfaces, etc. Examples of signal processingoperations that may be performed by the main controller 300 comprise,for example, filtering, amplification, analog-to-digital conversionand/or digital-to-analog conversion, up-conversion/down-conversion ofbaseband signals, encoding/decoding, encryption/decryption,modulation/demodulation, etc.

In conjunction with telematics related operations in the main controller300, the internal communication subsystem 320 may preferably supportand/or utilize wireless technologies that are suitable from long rangecommunications, including with remote peers—e.g., satellitecommunications (including bidirectional peer-to-peer communication;positioning satellite communication, such as GPS; etc.), cellularcommunications, etc. Further, the internal communication subsystem 320may be used to facilitate reception of data pertinent to telematicsoperations and/or operations of the main controller 300 as a whole. Forexample, the internal communication subsystem 320 may enable receiving(and providing the main processor 300 with) such data as locationinformation (e.g., GPS positioning based location information), controlsignals (e.g., from telematics servers), software updates (e.g., fromproviders, operators, etc.), and the like.

The external 3rd party communication equipment 362 may be substantiallysimilar to the internal communication subsystem 320. In this regard, theexternal 3rd party communication equipment 362 the may comprise suitablecircuitry and/or other related hardware for handling wired and/orwireless communications. For example, the external 3rd partycommunication equipment 362 may comprise a transceiver configured tohandle one or more of the wired and wireless technologies noted withrespect to the internal communication subsystem 320. However, theexternal 3rd party communication equipment 362 may be a dedicated,off-the-shelf system, and may be legacy and 3rd party system.Nonetheless the external 3rd party communication equipment 362 mayprovide the same type of communications, particularly with respect totelematics related operations, as the internal communication subsystem320. The external communication interface component 330 may be used toensure compatibility with and operability of different types ofcomponents systems.

The main controller 300 may be operable to interact with localcomponents and/or systems in conjunction with telematics relatedoperations. In this regard, the telematics host component 350 may beconfigured to function as a telematics host (e.g., a CANBus based host),to enable the main controller 300 to communicate with other externalcomponents or equipment (e.g., the legacy 3rd party telematics unit 370₂, external telematics unit 380, the next generation WCC unit 392, thenext generation welding UI 394, the next generation machine UI 396,etc.), using CANBus based communication protocols for example, toprovide telematics related data and/or control signals.

In operation, the main controller 300 may be configured to collect andprocess (format, process for communication, etc.) digital and analogtelematics related data. The telematics related data may includelocation, machine status, service info, engine sensor data, error codes,and other data available to the main controller 300. The main controller300 may obtained the data from the electronic ECU 364 (using thetelematics client component 340 to interface therewith). In instanceswhere the electronic ECU 364 may not be present or available to provideengine data 341, the main controller 300 may collect the informationdirectly (e.g., by interacting with analog sensors 360). The maincontroller 300 may provide the telematics related data to other localcomponents that would have obtained the data from the electronic ECU364—e.g., the 3rd party telematics units 370 ₁ and 370 ₂, externaltelematics unit 380. The main controller 300 may also communicate thatdata to remote entities (e.g., telematics servers, such as server 31 ofFIG. 1), such as using the internal communication subsystem 320 or 3rdparty external communication components.

In some instances, the main controller 300 may format the telematicsdata into a single standard format, such that equipment or devicesdriven by a particular engine may have only a single communicationsstandard to support. This may obviate the need to have the equipment ordevices also support other providers' telematics units (e.g., the 3rdparty telematics units 370 ₁ and 370 ₂). In other words, the maincontroller 300 may allow backward compatibility and/or compatibilitywith solutions by different providers, by performing the necessarydigitization and telematics formatting “translation.” For example, byprocessing the telematics data in the main controller 300, criticalengine related data (e.g., information relating to engine coolant,engine oil, fuel, etc.) may be available digitally to 3rd party CANBustelematics units 3rd party telematics units 370 ₂ in a singlestandardized format, simplifying installation by not having to spliceinto analog sensors. Further, the main controller 300 may also providethe additional benefit of supplying welding related data 301 in additionto traditional telematics data.

Where internal communication component (e.g., the internal communicationsubsystem 320) is used, no third party hardware is required, thusproviding superior value and reliability through system simplicity.Nonetheless, by incorporating support of external communicationequipment (e.g., by incorporating the external communication interface330), compatibility with legacy and/or 3rd party provider communicationcomponents may be ensured in a cost-effective manner. Accordingly, the3rd party communication equipment 362 may be easily and cost-effectivelyintegrated using standard generic communications like TCP/IP, with theexternal communication interface 330 providing the necessary TCP/IPprocessing, to connect to the modem. The 3rd party communicationequipment 362 may then allow remote connectivity, such as over theInternet, via satellite, cellular, WiFi, or any other wireless means.

In addition to the configuration illustrated in FIG. 3, otherconfigurations may be used or implemented using only some of theelements shown in FIG. 3 (e.g., based on availability, user or providerpreferences, etc.). FIGS. 4A through 7B show other, differentconfigurations that may be used in providing control of integratedtelematics, using only some of the components or equipment described orshown in FIG. 3.

FIG. 4A is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party telematics, andwithout engine control unit (ECU). Shown in FIG. 4A is a main controller400, the sensors 360, and the legacy 3rd party telematics units 370 ₁.

The main controller 400 may be similar to the main controller 300.However, the main controller 400 may have minimal implementation,comprising only the main processor 310. In the configuration shown inFIG. 4A, the main processor 310 may receive welding related data 401(similar to the welding related data 301 of FIG. 3). Further, the mainprocessor 310 may receive a telematics input 403, which may onlycomprise some of the telematics related sensory information generated bythe sensors 360. For example, the telematics input 403 may comprise onlysensory information corresponding to the auxiliary power transformersensor 360 ₁. Remaining telematics sensory data 461 (e.g., correspondingto battery voltage sensor 360 ₂ and engine sensors 360 ₃) may beprovided, as analog input(s), to the legacy 3rd party telematics unit370 ₁.

FIG. 4B is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party telematics, andwith engine control unit (ECU). Shown in FIG. 4B is the main controller400, the sensors 360, the legacy 3rd party telematics units 370 ₁, andthe electronic ECU 364 of FIG. 3.

As with the configuration depicted in FIG. 4A, the main processor 310may receive welding related data 301 and telematics input 303,comprising at least some of the telematics related sensory datagenerated by the sensors 360. The remaining telematics sensory data 361,however, may be sent to the electronic ECU 364, which may generatecorresponding data (e.g., as CANBus signal) for input into the legacy3rd party telematics unit 370 ₁.

FIG. 5A is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party telematics andtelematics modules, and without engine control unit (ECU). Shown in FIG.5A is a main controller 500, the sensors 360, the legacy 3rd partytelematics units 370 ₂, the external telematics unit 380, the nextgeneration WCC unit 392, the next generation welding UI 394, and thenext generation machine UI 396.

The main controller 500 may be similar to the main controller 300.However, the main controller 500 may have minimal implementation,comprising only the main processor 310, the telematics client component340, and the telematics host component 350. In other words, in theconfiguration shown in FIG. 5A (and similarly the configuration shown inFIG. 5B), the main controller 500 lacks the communication resources(e.g., the internal communication subsystem 320 and the externalcommunication interface component 330) needed to transmit the telematicsrelated information to remote entities, whether using internalcomponents or external equipment. Nonetheless, the main processor 310may receive the welding related data 301 and the telematics relatedsensory data 303 (from all sensors 360). Thus, the main controller 500may be operable to function as telematics host, providing telematicsdata (including welding related information) and related messaging(after processing and formatting) to local devices or equipment (e.g.,the legacy 3rd party telematics units 370 ₂, the external telematicsunit 380, the next generation WCC unit 392, the next generation weldingUI 394, and the next generation machine UI 396).

FIG. 5B is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party telematics, andwith engine control unit (ECU). Shown in FIG. 5B is the main controller500, the sensors 360, the legacy 3rd party telematics units 370 ₂, theexternal telematics unit 380, the next generation WCC unit 392, the nextgeneration welding UI 394, the next generation machine UI 396, and theelectronic ECU 364 of FIG. 3.

As with the configuration depicted in FIG. 5A, the main processor 310may receive welding related data 301. However, only some of thetelematics sensory information (e.g., sensory information correspondingto the corresponding to the auxiliary power transformer sensor 360 ₁)may be provided directly to the main processor (as input signal 521).Remaining telematics sensory data 523 (e.g., corresponding to thebattery voltage sensor 360 ₂ and the engine sensors 360 ₃), however, maybe sent to the electronic ECU 364, which may generate corresponding data(e.g., as CANBus signal) for input, as input signal 525, into the maincontroller 500, via the telematics client component 340.

FIG. 6A is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party wirelesscommunication components, and without engine control unit (ECU). Shownin FIG. 6A is a main controller 600, the sensors 360, the external 3rdparty communication equipment 362, the legacy 3rd party telematics units370 ₂, the external telematics unit 380, the next generation WCC unit392, the next generation welding UI 394, and the next generation machineUI 396.

The main controller 600 may be similar to the main controller 300.However, the main controller 600 may be a reduced implementation,comprising only the main processor 310, the external communicationinterface component 330, the telematics client component 340, and thetelematics host component 350. In other words, in the configurationshown in FIG. 6A (and similarly the configuration shown in FIG. 6B), themain controller 600 lacks internal/integrated communication resources(e.g., the internal communication subsystem 320) needed to autonomouslytransmit the telematics related information to remote entities and/orautonomously receiving data (e.g., location, control, software updates,etc.). Rather, communications can only be done using externalcommunication resources, such as the external 3rd party communicationequipment 362, which the main controller 600 may interact with using theexternal communication interface component 330. The main processor 310may receive the welding related data 301 and the telematics relatedsensory data 303 (from all sensors 360). The main controller 600 may beoperable to function as telematics host, providing telematics data(including welding related information) and related messaging (afterprocessing and formatting) to local devices or equipment (e.g., thelegacy 3rd party telematics units 370 ₂, the external telematics unit380, the next generation WCC unit 392, the next generation welding UI394, and the next generation machine UI 396).

FIG. 6B is a block diagram illustrating an example configuration forcontrolling telematics integration using basic 3rd party wirelesscommunication components and engine control unit (ECU). Shown in FIG. 6Bis the main controller 600, the sensors 360, the external 3rd partycommunication equipment 362, the legacy 3rd party telematics units 370₂, the external telematics unit 380, the next generation WCC unit 392,the next generation welding UI 394, the next generation machine UI 396,and the electronic ECU 364.

As with the configuration depicted in FIG. 6A, the main processor 310may receive welding related data 301. However, only some of thetelematics sensory information (e.g., sensory information correspondingto the corresponding to the auxiliary power transformer sensor 360 ₁)may be provided directly to the main processor (as input signal 621).Remaining telematics sensory data 623 (e.g., corresponding to thebattery voltage sensor 360 ₂ and the engine sensors 360 ₃), however, maybe sent to the electronic ECU 364, which may generate corresponding data(e.g., as CANBus signal) for input, as input signal 625, into the maincontroller 500, via the telematics client component 340.

FIG. 7A is a block diagram illustrating an example configuration forcontrolling telematics integration using internal wireless communicationcomponents, and without engine control unit (ECU). Shown in FIG. 7A is amain controller 700, the sensors 360, the external 3rd partycommunication equipment 362, the legacy 3rd party telematics units 370₂, the next generation WCC unit 392, the next generation welding UI 394,and the next generation machine UI 396.

The main controller 700 may be similar to the main controller 300.However, the main controller 700 may be a reduced implementation,comprising only the main processor 310, the external communicationinterface component 330, the telematics client component 340, and thetelematics host component 350. In other words, in the configurationshown in FIG. 7A (and similarly the configuration shown in FIG. 7B), themain controller 700 lacks capabilities to support use of externalcommunication resources (e.g., the external 3rd party communicationequipment 362). Instead, the main controller 700 only supports use ofintegrated communication resources (i.e., the internal communicationsubsystem 320), thus it would still enable autonomous transmission ofthe telematics related information to remote entities and/or autonomousreception of data (e.g., location, control, software updates, etc.).

The main processor 310 may receive the welding related data 301 and thetelematics related sensory data 303 (from all sensors 360). The maincontroller 700 may be operable to function as telematics host, providingtelematics data (including welding related information) and relatedmessaging (after processing and formatting) to local devices orequipment (e.g., the legacy 3rd party telematics units 370 ₂, theexternal telematics unit 380, the next generation WCC unit 392, the nextgeneration welding UI 394, and the next generation machine UI 396).

FIG. 7B is a block diagram illustrating an example configuration forcontrolling telematics integration using internal wireless communicationcomponents, and with engine control unit (ECU). Shown in FIG. 7B is themain controller 700, the sensors 360, the external 3rd partycommunication equipment 362, the legacy 3rd party telematics units 370₂, the external telematics unit 380, the next generation WCC unit 392,the next generation welding UI 394, the next generation machine UI 396,and the electronic ECU 364.

As with the configuration depicted in FIG. 7A, the main processor 310may receive welding related data 301. However, only some of thetelematics sensory information (e.g., sensory information correspondingto the corresponding to the auxiliary power transformer sensor 360 ₁)may be provided directly to the main processor (as input signal 721).Remaining telematics sensory data 723 (e.g., corresponding to batteryvoltage sensor 360 ₂ and engine sensors 360 ₃), however, may be sent tothe electronic ECU 364. The ECU 364 may generate corresponding data(e.g., as CANBus signal) for input, as input signal 725, into the maincontroller 700, via the telematics client component 340.

The present methods and systems may be realized in hardware, software,or a combination of hardware and software. The present methods and/orsystems may be realized in a centralized fashion in at least onecomputing system, or in a distributed fashion where different elementsare spread across several interconnected computing systems. Any kind ofcomputing system or other apparatus adapted for carrying out the methodsdescribed herein is suited. A typical combination of hardware andsoftware may include a general-purpose computing system with a programor other code that, when being loaded and executed, controls thecomputing system such that it carries out the methods described herein.Another typical implementation may comprise an application specificintegrated circuit or chip. Some implementations may comprise anon-transitory machine-readable (e.g., computer readable) medium (e.g.,FLASH drive, optical disk, magnetic storage disk, or the like) havingstored thereon one or more lines of code executable by a machine,thereby causing the machine to perform processes as described herein.

While the present method and/or system may be described with referenceto certain implementations, it will be understood by those skilled inthe art that various changes may be made and equivalents may besubstituted without departing from the scope of the present methodand/or system. In addition, many modifications may be made to adapt aparticular situation or material to the teachings of the presentdisclosure without departing from its scope. Therefore, it is intendedthat the present method and/or system not be limited to the particularimplementations disclosed, but that the present method and/or systemwill include all implementations falling within the scope of theappended claims.

As utilized herein the terms “circuits” and “circuitry” refer tophysical electronic components (i.e. hardware) and any software and/orfirmware (“code”) which may configure the hardware, be executed by thehardware, and or otherwise be associated with the hardware. As usedherein, for example, a particular processor and memory may comprise afirst “circuit” when executing a first set of one or more lines of codeand may comprise a second “circuit” when executing a second set of oneor more lines of code. As utilized herein, “and/or” means any one ormore of the items in the list joined by “and/or”. As an example, “xand/or y” means any element of the three-element set {(x), (y), (x, y)}.In other words, “x and/or y” means “one or both of x and y”. As anotherexample, “x, y, and/or z” means any element of the seven-element set{(x), (y), (z), (x, y), (x, z), (y, z), (x, y, z)}. In other words, “x,y and/or z” means “one or more of x, y and z”. As utilized herein, theterm “example” means serving as a non-limiting example, instance, orillustration. As utilized herein, the terms “e.g. and for example” setoff lists of one or more non-limiting examples, instances, orillustrations. As utilized herein, circuitry is “operable” to perform afunction whenever the circuitry comprises the necessary hardware andcode (if any is necessary) to perform the function, regardless ofwhether performance of the function is disabled or not enabled (e.g., bya user-configurable setting, factory trim, etc.).

What is claimed is:
 1. A system for use in welding-type operations, thesystem comprising: a welding supply source configured to provide weldingoutputs to drive a welding torch, the welding outputs comprising atleast one of power or weld material; an engine configured to drive thesystem; and a controller configured to: obtain telematics datacomprising at least data relating to at least one component of thesystem; and process the telematics data to enable use of the telematicsdata by a remote entity for at least one of remote monitoring ormanagement of at least one component of the system, wherein theprocessing comprises modifying or configuring the telematics data tomatch a single standard; wherein the controller is configured tofunction concurrently as a telematics client node and a telematics hostnode.
 2. The system of claim 1, wherein the controller is operable toobtain at least part of the telematics data from one or more analogsensors.
 3. The system of claim 1, wherein the controller is operable toobtain at least part of the telematics data from an engine control unit(ECU) of the engine.
 4. The system of claim 1, wherein the telematicsdata comprises engine related data that comprises information relatingto at least one of engine coolant, engine oil, or engine fuel.
 5. Thesystem of claim 1, wherein the controller is to process the telematicsdata by formatting the telematics data in accordance with a singlestandard format regardless of source or type of obtained data.
 6. Thesystem of claim 1, wherein the controller is to process the telematicsdata by digitizing obtained analog data.
 7. The system of claim 1,wherein the controller is to process the telematics data by processingthe telematics data for communication to the remote entity in accordancewith a wired or wireless interface, protocol, or standard.
 8. The systemof claim 1, wherein the controller is operable to communicate telematicsrelated messages at least one of with the engine, a component of theengine, or one or more components in accordance with a communicationprotocol.
 9. The system of claim 8, wherein the communication protocolcomprises controller area network (CANBus) protocol.
 10. A system forhandling telematics data associated with a welding-type arrangement,comprising: a controller that comprises: an interface component operableto receive telematics data; a telematics host component operable toperform telematics host node functions; a telematics client componentoperable to perform telematics client node functions; and a processingcircuit operable to process the telematics data, to enable use of thetelematics data by a remote entity; wherein: the telematics datacomprises at least data relating to one or more components of thewelding-type arrangement; and the processing comprises modifying orconfiguring the telematics data to match a single standard supported orused by the remote entity.
 11. The system of claim 10, wherein theprocessing circuit is operable to format the telematics data inaccordance with a single standard format regardless of source or type ofobtained data.
 12. The system of claim 10, wherein the processingcircuit is operable to digitize obtained analog data.
 13. The system ofclaim 10, wherein the controller comprises at least one of: an internalcommunication component operable to at least one of configure, setup, orutilize at least one of wired or wireless connections, to the remoteentity; and an external communication interface component operable toconnect the controller to an external communication device that providesat least one of wired or wireless connections to the remote entity. 14.The system of claim 13, wherein at least one of the processing circuit,the communication component, or the external communication interfacecomponent are operable to process the telematics data for communicationsvia the wired or wireless connections to the remote entity.
 15. Thesystem of claim 10, wherein the controller comprises a telematicscommunication component operable to handle telematics related messagingin accordance with a particular telematics communication protocol. 16.The system of claim 15, wherein the telematics communication protocolcomprises a controller area network (CANBus) protocol.
 17. A method,comprising: handling in a controller of a welding-type arrangement,telematics data associated with the welding-type arrangement, thehandling comprising: obtaining telematics data, wherein during obtainingof the telematics data the controller functions concurrently as atelematics client node and a telematics host node; processing thetelematics data comprises formatting the telematics data in accordancewith a single standard, to enable use of the telematics data by theremote entity; and communicating the telematics data to the remoteentity, wherein the telematics data comprises at least data relating toone or more components of the welding-type arrangement.
 18. The methodof claim 17, wherein processing the telematics data comprises formattingthe telematics data in accordance with a single standard formatregardless of source or type of obtained data.
 19. The method of claim17, further comprising processing the telematics data for communicationto the remote entity in accordance with a wired or wireless interface,protocol, or standard.
 20. The method of claim 17, wherein thetelematics data comprises analog data, and wherein processing thetelematics data comprises digitizing the analog data.